Wireless/lan router queuing method and system

ABSTRACT

A queuing method and system for wireless/LAN routers processes and routes an incoming data packet from a wireless mobile network to a destination server. The system uses a wireless transport module to initiate storage of the data packet in a permanent storage device while simultaneously forwarding the data packet to the destination server. A database thread is used to manage the operations being performed on the data packet and for initiating the storage of the data packet in a permanent storage device based on a permanent storage queue. A main thread is used to simultaneously forward the data packet to the destination server. The wireless transport module is adapted to determine whether the data packet has been acknowledged by the destination server and aborting the storage of the data packet in the permanent storage device once acknowledgment from by destination server has been received.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/868,116, filed Oct. 5, 2007, which is a continuation of U.S. patentapplication Ser. No. 10/324,481, filed on Dec. 19, 2002. U.S. patentapplication Ser. No. 10/324,481 issued to patent as U.S. Pat. No.7,296,067. The entire contents of application Ser. No. 11/868,116, andapplication Ser. No. 10/324,481, are hereby incorporated by reference.

TECHNICAL FIELD

This invention relates to wireless networks and more particularly to aqueuing method and system for wireless/LAN routers.

BACKGROUND

The delivery of text-based messages (i.e. data packets) from a sendingdevice to one or more receiving devices over a wireless LAN, presentsspecial challenges. Typically, the message is routed through a wirelessgateway where it is temporarily stored until it has been transmitted to,and stored within, an electronic mail server of the data network.Receiving devices are then able to retrieve stored messages from theelectronic mail server at their convenience. The speed at whichelectronic messages are transmitted from a sending to a receiving devicedepends in part on how efficiently data packets are transported from asending mobile device to an electronic mail server through wirelesscommunication networks.

When a wireless gateway receives a data packet from a mobile device overa wireless network, the received data packet is sent to a destinationelectronic mail server. However, to ensure that the data packet issuccessfully transmitted to the destination electronic mail server andnot lost in the meantime, the wireless gateway generally stores the datapacket in an internal permanent storage device (e.g. a database serveror a file system) before transmitting the data packet. Typically, thewireless gateway waits until the permanent storage device confirmsstorage of the data packet before proceeding with processing the datapacket or even with sending acknowledgement of the receipt of the datapacket back to the mobile device. This kind of storage procedureappreciably slows down the processing of data packets within the router.

SUMMARY

The invention provides in one aspect, a method of processing and routinga data packet from a wireless mobile network to a destination server,said method comprising the steps:

receiving the incoming data packet from the wireless mobile network;

initiating the storage of the data packet in a permanent storage devicebased on a permanent storage queue;

simultaneously delivering the data packet to the destination serverbased on a main queue;

determining whether the data packet has been acknowledged by thedestination server; and

aborting the storage of the data packet in the permanent storage deviceif the data packet has been acknowledged by the destination server andif the storage of the data packet has not been completed.

In another aspect, the present invention provides a system forprocessing and routing an incoming data packet from a wireless mobilenetwork to a destination server, the system comprising:

a wireless transport module for receiving the incoming data packet fromthe wireless mobile network;

a permanent storage device associated with the wireless transport modulefor storing the data packet until acknowledgement of the data packetfrom the destination server;

a database thread associated with the wireless transport module adaptedto manage the operations being performed on the data packet and forinitiating the storage of the data packet in a permanent storage devicebased on a permanent storage queue;

a main thread associated with the wireless transport module forsimultaneously delivering the data packet to the destination serverbased on a main queue;

said wireless transport module being adapted to determine whether thedata packet has been acknowledged by the destination server and abortingthe storage of the data packet in the permanent storage device if thedata packet has been acknowledged by the destination server and if thestorage of the data packet has not been completed.

In another aspect, the present invention provides a computer-readablemedium having stored thereon a set of instructions, said set ofinstructions, which when executed, perform the steps comprising:

receiving an incoming data packet from a wireless mobile network;

initiating the storage of the data packet in a permanent storage devicebased on a permanent storage queue;

simultaneously delivering the data packet to the destination serverbased on a main queue;

determining whether the data packet has been acknowledged by thedestination server; and

aborting the storage of the data packet in the permanent storage deviceif the data packet has been acknowledged by the destination server andif the storage of the data packet has not been completed.

Further aspects and advantages of the invention will appear from thefollowing description taken together with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

In the accompanying drawings:

FIG. 1 is a schematic diagram of one embodiment of the wireless gatewayof the present invention and the surrounding network environment;

FIG. 2 is a schematic diagram of the database thread that manages thepermanent storage queue implemented in the wireless transport module andutilized to store data packets within the permanent storage device ofFIG. 1;

FIG. 3 is an event sequence diagram that illustrates the typical dataflow of a data packet sent from mobile device to destination electronicmail server through wireless connector system of FIG. 1;

FIG. 4 is a finite state machine representation of the functionality ofthe database thread of FIG. 2; and

FIG. 5 is a schematic diagram illustrating an example of a permanentstorage queue utilized to store data packet operations within thepermanent storage device of FIG. 1.

DETAILED DESCRIPTION

FIG. 1 illustrates the main elements of a wireless gateway 10 built inaccordance with a preferred embodiment of the invention. Specifically,wireless gateway 10 is adapted to route data packets 15 received from amobile data communication device 14 over wireless mobile network 16 to adestination electronic mail server 18 through a wireless connectorsystem 20. Specifically, wireless communication network 10 allows for amore efficient routing of data packets 15 (i.e. messages) from mobiledevice 14 to destination electronic mail server 18 through wirelessgateway 10 while still providing a high degree of data packet safety.

Mobile device 14 is any commercially available mobile data communicationdevice adapted to transmit data packets 15 to wireless mobile network 16(e.g. IEEE 802.11 standard) or any other wireless protocol for wirelesscommunication. In a preferred embodiment mobile device 14 is a hand-heldtwo-way wireless paging device, however, mobile device 14 could,alternatively be any other type of mobile communication device capableof sending and receiving messages via wireless mobile network 16, suchas two-way paging computers, personal digital assistants (PDAs),portable electronic messaging devices, cellular phones, or handhelde-mail clients.

Wireless mobile network 16 is preferably a wireless packet data network,(e.g. Mobitex™ or DataTAC™), which provides radio coverage to mobiledevices 14 and has limited bandwidth capabilities, although it could beany other types of commercially available wireless networks. Dependingon the type of wireless mobile network 16 utilized, it may be necessaryto route data packets 15 between a TCP wireless gateway 10 connectionand an X.25 or IP address mobile network connection and vice versa usingan intermediary routing mechanism that provides TCP clients access to anX.25 connection. As is conventionally, known such a wireless mechanismcould use NET ID (DataTAC) or FST MAN (Mobitex) to connect to wirelessmobile network 16.

Wireless gateway 10 forms a connection or bridge between the servers andwireless networks associated with wireless e-mail communication.Specifically, wireless gateway 10 is coupled between wireless LAN 16 andthe hardwired data network that includes wireless connector system 20and destination electronic mail server 18. Wireless gateway 10 includesa permanent storage device 22 and a wireless transport module 24.

Permanent storage device 22 can be implemented by any commerciallyavailable database server with the appropriate speed and storagecapacity. Permanent storage device 22 contains system configurationinformation, system state data, and tables that store mobile device 14information.

Wireless transport module 24 is the interface between mobile device 14and wireless gateway 10. Specifically, wireless transport module 24communicates with wireless mobile network 16 using the intermediaryrouting mechanism discussed above (provides TCP clients access to anX.25 or UDP connection) and assembles data packets 15 being receivedfrom mobile device 14 over wireless mobile network 16. Once data packets15 are assembled, they are sent to the upper layer of the wirelesstransport module 24 for simultaneous storage in permanent storage device22 and processing through wireless gateway 10 to wireless connectionsystem 20 and eventually to destination electronic mail gateway 18.

Wireless connector system 20 is part of the wired, backbone network andis coupled to wireless gateway 10. Wireless connector system 20communicates with wireless gateway 10 and each electronic message serverthat connects to wireless gateway as a unique address called a UID or anSRP ID.

Destination electronic mail server 18 is coupled to wireless connectorsystem 20 and is a conventional electronic mail server (e.g. ExchangeServer manufactured by Microsoft of Seattle, Wash.). It should beunderstood that any other commercially available electronic mail servercould be utilized within wireless gateway 10. For purposes ofillustration, only destination electronic mail server 18 has beendiscussed as a possible destination, although it should be understoodthat the inventive method of wireless gateway 10 is applicable tovarious types of destination devices and communication service (e.g.weather service, news service, stock quote service, etc.)

Now referring to FIGS. 1 and 2, according to the queuing method of thepresent invention, when wireless gateway 10 receives a data packet 15from wireless mobile network 16, wireless transport module 24 routes thedata packet to the electronic mail server 18 (path A on FIG. 1) whilesimultaneously to write data packet 15 into permanent storage device 22(path B on FIG. 1). These two actions are conducted in parallel usingseparate but concurrently running computational threads. Specifically, adatabase thread is used to write data packet 15 into the permanentstorage device 22 and a main thread is used to forward data packet 15 tothe destination server 18.

The main thread is used to forward data packet 15 to destinationelectronic mail server 18 through wireless connector system 20. The mainthread manages the transport of data packets 15 to destinationelectronic mail server 18 using a main queue. In many cases wirelessgateway 10 can deliver a data packet to a destination address (e.g.destination electronic mail server 18) using main thread, faster than itcan write the data packet to permanent storage device 22. In such cases,the method of the present invention achieves a more efficient throughputof data packet 15 through wireless gateway 10 since it is not necessaryto devote processing time to the storage of data packet 15 in permanentstorage device 22.

The database thread shown in FIG. 2 is used to manage and coordinate thestorage of data packets 15 in permanent storage device 22. The databasethread manages the storage of data packets 15 within permanent storagedevice 22 using a permanent storage queue. Individual worker threads(not shown) are associated with the three basic operations that arecarried out on data packets 15, namely “insert”, “update” and “delete”.When wireless gateway 10 receives a message from mobile device 14, an“insert” operation is posted. When the routing endpoint (i.e. theconnection point) within the wireless gateway 10 has been located, thenthe message is updated in the permanent storage device 22 using the“update” operation to reflect the routing information within wirelessgateway 10. The wireless gateway 10 routing data is saved in the eventof a component failure or work re-distribution. When an“acknowledgement” message is received from wireless connector system 20,then a “delete” operation is posted.

Database thread keeps track (and updates it as necessary) of theoperation that is being performed on the data packet and acts as anintelligent buffer between wireless transport module 24 and thepermanent storage device 22. At any one time, there is at most onepending operation. It should be noted that when an “update” operation isreceived following the initial “insert” operation, data packet 15 isoperated on in place (i.e. within wireless gateway 24) along with theassociated queue entry within database thread to reduce memory and CPUoverhead. Also, if an “update” operation is posted before the “insert”operation can occur, then the data packet 15 to be inserted is changedto reflect the update in place. The “insert” operation will thencontinue as normal. If an “update” operation is posted after the“insert” operation has been completed, then the “update” operation issubmitted to the permanent storage queue. If the “delete” operation isposted before an “update” operation can occur, then the “update”operation is removed from the permanent storage queue and replaced withthe “delete” operation. Accordingly, the work in the queue reflects thecurrent state/operation of the message. This allows wireless gateway 10to more efficiently process data messages since there is no storage ofadditional operations as is normally the case.

FIG. 3 is an event sequence diagram that illustrates an example dataflow of data packet 15 sent by mobile device 14 to destinationelectronic mail server 18.

Specifically, data packet 15 is sent from mobile device 14 to wirelesstransport module 22 at (100). At (102), wireless transport module 24initiates the storage of data packet 15 into a table within permanentstorage device 22 by the associated “insert” operation within thepermanent storage queue. The specific operation of permanent storagequeue is detailed in detail below in association with FIG. 4. Datapacket 15 is then simultaneously forwarded to destination electronicmail server 18 at (104). Specifically, wireless transport module 24determines the type of destination device to which data packet 15 isbeing sent to and implements appropriate data packet handling stepsdepending on the destination device type.

At (105), when the location of the routing endpoint within wirelessgateway 10 is located, wireless transport module 24 posts an “update”operation from mobile device 14. That is, the message is to be updatedin permanent storage device 22 to reflect this discovered routinginformation. At (106), destination mail server 18 sends anacknowledgement (or refusal) to wireless transport module 24. Inresponse, at (108) wireless transport module 24 carries out the “delete”operation. Specifically, in the case where data packet 15 has alreadybeen inserted into permanent storage device 22, wireless transportmodule 24 deletes data packet 15 from permanent storage device 22.Alternatively, in the case where the “insert” operation associated withdata packet 15 is still in the permanent storage queue, wirelesstransport module 24 removes this “insert” operation from the permanentstorage queue so that data packet 15 is not written to permanent storagedevice 22. It should be understood that these actions would also beperformed by wireless transport module 24 in the case where data packet15 has “expired”, that it is not possible to reach the intendeddestination within a configurable period of time. Wireless transportmodule 24 sends an internal status acknowledgement confirming thatmessage delivery is complete once data packet 15 is inserted intopermanent storage device 22 or if data packet 15 is delivered todestination server 18. This step can also involve deletion of datapacket 15 from various other local memories within wireless gateway 10.

FIG. 4 is a finite state machine illustrating how the database threadmanages the “insert”, “update” and “delete” operations that are appliedto a data packet 15 within the permanent storage queue. As discussedabove, database thread manages the position and content of the variousoperations within permanent storage queue to provide an efficientutilization of permanent storage device 22. Specifically, the databasethread combines data packet 15 operations in order to minimize thenumber of storage operations. That is, there is at most one operationfor any data packet 15 within the permanent storage queue. The databasethread also prioritizes data packet 15 operations within permanentstorage queue to minimize the number of storage operations as will bediscussed in respect of FIG. 5.

As shown, an “insert” data packet 15 operation is first received bywireless transport module 22 at (200). Then at (202), the databasethread places the “insert” operation within the permanent storage queueand the main queue simultaneously.

At (202), if destination electronic mail server 18 sends an“acknowledgement” at (204) then at (206), the pending “insert” operationfor that data packet 15 in the permanent storage queue is removed. Thatis, in the case where data packet 15 is delivered to destination server18 faster than the database thread causes data packet 15 to be insertedinto permanent storage device 22, it is possible to avoid having toaccess permanent storage device 22. Accordingly, it is possible,depending on the availability and response time of the destinationdevices at issue, to eliminate a substantial proportion of access topermanent storage device 22.

Alternatively, if at (202), if the “insert” operation reaches the top ofthe permanent storage queue at (205), then data packet 15 is written topermanent storage device 22 at (207). If destination electronic mailserver 18 sends an “acknowledgement” at (222), then at (224), the“delete” operation is placed within permanent storage queue to effectthe removable of data packet 15 from the appropriate storage table inpermanent storage device 22. If an “update” operation is received at(214) prior to the “acknowledgement” from destination server 18 (222),then at (216), the “update” operation is placed in the permanent storagequeue. Once the “acknowledgement” is received from destination server18, the “update” operation is replaced with a “delete” operation in thepermanent storage queue at (221).

Alternatively, at (202) if an “update” operation is posted by wirelessgateway 10 (i.e. routing endpoint has been located) at (208), beforedata packet 15 reaches and is acknowledged by destination electronicmail server 18 and before the top of the permanent storage queue isreached, then the initial “insert” operation is replaced with a revised“insert” operation in the permanent storage queue at (210). This revised“insert” operation consists of an updated version of the original datapacket 15 that was to be initially inserted. That is, if an insertoperation has not yet been performed on permanent storage device 22(i.e. the “insert” operation is still in the permanent storage queue),then the initial “update” operation and the later sent “insert”operation are combined into a new “insert” command. Accordingly, thesetwo operations are consolidated into one for placement in the permanentstorage queue reducing prospective storage operations.

At (210), if the “insert” operation reaches the top of the permanentstorage queue at (209) then at (207), the data packet 15 is written topermanent storage device 22 according to the revised “insert” operation(which combined the original “insert” operation and the “update”operation). When an “acknowledgement” is received from destinatione-mail server 18 at (222), the “delete” operation is placed in thepermanent storage queue at (224) to effect removal of data packet 15from the table in permanent storage device 22. Again, if an “update”operation is received at (214) prior to the “acknowledgement” fromdestination server 18, then at (216), the “update” operation is placedin the permanent storage queue. Once the “acknowledgement” is receivedfrom destination server 18, the “update” operation is replaced with a“delete” operation in the permanent storage queue at (221).

Alternatively, if at (210), electronic mail server 18 sends an“acknowledgement” at (212) then at (213) the pending “insert” operationis removed from the permanent storage queue. This is done, since datapacket 15 has not been written to permanent storage device 22 andaccordingly, there is no need to evoke the “delete” operation to removeit from storage.

FIG. 5 illustrates an example of a permanent storage queue for wirelesstransport module 24 of wireless gateway 10. Each data packet 15 inpermanent storage queue is placed there to be forwarded to permanentstorage device 22 for storage and each data packet operation isassociated with a particular destination device. Again, while thedestination device in the illustrative example of FIG. 1 is adestination electronic mail server 18, it should be understood thatvarious types of destination devices could be accommodated.

The database thread of wireless transport module 22 optimizes theprocessing of data packets 15 through strategic placement of datapackets 15 operations within the permanent storage queue. Normally,queue elements are ordered in the permanent storage queue based on theorder of arrival of the message from mobile device 22. That is, theintroduction of an “update” or “delete” operation will not change theorder of the element in the queue. However, in wireless gateway 10,database thread prioritizes data packet 15 operations in the permanentstorage queue according to the time is takes to send data packet 15 andto receive the acknowledgement of reception from a destination devicefor a particular destination device. Specifically, database thread keepsa running record log of the average length of time required on averagefor a data packet 15 to be sent to a particular destination device. Theinverse of a measure of the average delivery time is then used to queuedata packet 15 operations in the permanent storage queue. That is, if adestination device is known to reply quickly (i.e. has in the pastreplied quickly) to wireless gateway 10 then it is advantageous toposition the associated data packet 15 operation near the bottom of thepermanent storage queue to provide delay to avoid processing theassociated data packet 15 operation (i.e. storing data packet or anupdate in permanent storage). In this way storage processing costsassociated with storing data packet 15 in permanent storage device 22can be reduced.

It is preferable to use the inverse of the moving average of thedelivery time of data packet 15 to a destination device to determine theposition of a data packet 15 operation within permanent storage device22 instead of average delivery time. Specifically, it has beendetermined that it is desirable to keep track of delivery times for thepast 10 messages. By using a moving average measure, wireless gateway 10is able to react much faster to changes in the state of the destinationdevice and the overall communication network. For example, when adestination device dies (i.e. becomes unreachable), the moving averagewill reflect the delay in packet delivery for that destination devicemuch faster than an average count would. Another example, where themoving average approach is preferable is where the destination device istoo overloaded with work (i.e. “too busy”) to reply.

For example, as shown, data packet operation “X” is positioned at thetop of the permanent storage queue and is associated with data packet Xand destination device A. Data packet operation “Y” is positioned nearthe bottom of the permanent storage queue and is associated with datapacket Y and destination device B. As shown, data packet operation “Z”is now being entered by database thread into permanent storage queue. Ifit is determined that the average of the delivery time (i.e. the timerequired to send and receive acknowledgement back from destinationdevice) of data packet Z to destination device C is shorter than thatassociated with data packet operation “Y”, then data packet operation“Z” will be placed below “Y” within the permanent storage queue asshown. Since data packet operation “Z” will be positioned below datapacket operation “Y”, it is increasingly possible that destinationdevice C will acknowledge receipt of data packet Z before data packetoperation “Z” reaches the top of the queue. In such a case, theprocessing time associated with storing data packet Z will be saved.

Further, other factors relating to the accessibility of the destinationdevice at issue are taken into account when positioning a data packet 15operation in the permanent storage queue. For example, in a case wherethere it is determined that a destination device in not connected withinthe network 10, the database thread automatically puts the associateddata packet 15 operation at the top of the permanent storage queue.Similarly, where the destination device specified with the data packet15 is “invalid” then main thread causes wireless transport module 24 toprovide an emergency message back to mobile device 14.

Finally, it is preferred that the main thread places data packet 15operations within main queue based on the moving average delivery timefor previous data sent to the destination device. However, it is alsopossible for main thread to arrange data packet 15 operations accordingto the First In First Out (FIFO) standard. That is, queue elements areordered in the main queue based on the arrival of the message frommobile device 14.

It has been determined by the inventors that by constructing permanentstorage queue such that memory storage operations are first attempted incases where data packet 15 is unlikely to be received and acknowledgedby destination electronic mail server 18 before it can be stored withinpermanent storage device 22 (i.e. in the case of slow or off-linedestination devices), the efficiency of storage operations can besubstantially improved. Also, increased throughputs of data packets 15have been observed, namely, an increase in message processing fromapproximately 12 messages per second to approximately 200 messages persecond under spike load and approximately 150 messages per second for asustained load.

It should be understood that while the specific communication equipmenthas been chosen and discussed for illustrative purposes, the presentinvention is applicable to any type of network routing system, includingwireless LAN routes, LAN to LAN routers, router-based communicationnetworks having dial-up users, and other general router-basedcommunication networks.

Accordingly, wireless gateway 10 allows for improved routing of datapackets to a destination server 18 while still guaranteeing a highdegree of data safety. Specifically, by simultaneous forwarding of datapackets 15 to permanent storage device 22 and destination electronicmail server 18, since for the cases where data packets 15 are receivedby a destination device and removed from the permanent storage queue,there is no requirement to perform costly permanent storage operations.By reducing the number of permanent storage device writing operations,wireless gateway 10 is able to handle a substantially higher volume ofmessages then would otherwise be the case where data packets 15 arefirst stored within a wireless gateway before being forwarded to adestination device. Further, this approach reduces the network trafficbetween wireless transport module 24 and permanent storage device 22 andthe associated CPU usage for both wireless transport module 24 andpermanent storage device 22. Finally, this approach reduces theeffective cost of hardware since it is possible to achieve a highervolume of processing using the same hardware.

As will be apparent to those skilled in the art, various modificationsand adaptations of the structure described above are possible withoutdeparting from the present invention, the scope of which is defined inthe appended claims.

1. A method of storing a data packet in a storage device, the methodcomprising: receiving an insert data packet operation by a wirelesstransport module, wherein the insert data packet operation has beentransmitted to a destination device; placing the insert data packetoperation into a storage queue; and removing the insert data packetoperation from the storage queue if an acknowledgement of the datapacket is received from the destination device and if the data packethas not been written to the storage device.
 2. The method of claim 1,further comprising writing the data packet to the storage device if theacknowledgement of the data packet has not yet been received from thedestination device and if the insert data packet operation is at the topof the storage queue.
 3. The method of claim 2, further comprisingplacing a delete data packet operation in the storage queue to effectremoval of the data packet from the storage device if theacknowledgement of the data packet is received from the destinationdevice after the data packet is written to the storage device.
 4. Themethod of claim 2, further comprising placing an update data packetoperation in the storage queue if the update data packet operation isreceived by the wireless transport module and if the acknowledgement ofthe data packet has not yet been received from the destination device.5. The method of claim 4, further comprising replacing the update datapacket operation with a delete data packet operation in the storagequeue to effect removal of the data packet from the storage device ifthe acknowledgement of the data packet is received from the destinationdevice after the update data packet operation is placed in the storagequeue.
 6. The method of claim 1, further comprising replacing the insertdata packet operation in the storage queue with a revised insert datapacket operation if an update data packet operation is received by thewireless transport module, if the acknowledgement of the data packet hasnot yet been received from the destination device, and if the insertdata packet operation is not at the top of the storage queue.
 7. Themethod of claim 6, wherein the revised insert data packet operationcomprises an updated version of the data packet.
 8. The method of claim7, further comprising writing the updated version of the data packet tothe storage device if the acknowledgement of the data packet has not yetbeen received from the destination device and if the revised insert datapacket operation is at the top of the storage queue.
 9. The method ofclaim 8, further comprising placing a delete data packet operation inthe storage queue to effect removal of the updated version of the datapacket from the storage device if the acknowledgement of the data packetis received from the destination device after the updated version of thedata packet is written to the storage device.
 10. The method of claim 8,further comprising placing a second update data packet operation in thestorage queue if the second update data packet operation is received bythe wireless transport module and if the acknowledgement of the datapacket has not yet been received from the destination device.
 11. Themethod of claim 10, further comprising replacing the second update datapacket operation with a delete data packet operation in the storagequeue to effect removal of the updated version of the data packet fromthe storage device if the acknowledgement of the data packet is receivedfrom the destination device after the second update data packetoperation is placed in the storage queue.
 12. The method of claim 7,further comprising removing the revised insert data packet operationfrom the storage queue if an acknowledgement of the data packet isreceived from the destination device and if the updated version of thedata packet has not been written to the storage device.
 13. The methodof claim 1, wherein the method is implemented at least one databasethread.
 14. A device comprising a wireless transport module, wherein thedevice is configured to: receive an insert data packet operation,wherein the insert data packet operation has been transmitted to adestination device; place the insert data packet operation into astorage queue; and remove the insert data packet operation from thestorage queue if an acknowledgement of the data packet is received fromthe destination device and if the data packet has not been written tothe storage device.
 15. The device of claim 14, wherein the device isfurther configured to write the data packet to the storage device if theacknowledgement of the data packet has not yet been received from thedestination device and if the insert data packet operation is at the topof the storage queue.
 16. The device of claim 15, wherein the device isfurther configured to place a delete data packet operation in thestorage queue to effect removal of the data packet from the storagedevice if the acknowledgement of the data packet is received from thedestination device after the data packet is written to the storagedevice.
 17. The device of claim 15, wherein the device is furtherconfigured to place an update data packet operation in the storage queueif the update data packet operation is received by the wirelesstransport module and if the acknowledgement of the data packet has notyet been received from the destination device.
 18. The device of claim17, wherein the device is further configured to replace the update datapacket operation with a delete data packet operation in the storagequeue to effect removal of the data packet from the storage device ifthe acknowledgement of the data packet is received from the destinationdevice after the update data packet operation is placed in the storagequeue.
 19. The device of claim 14, wherein the device is furtherconfigured to replace the insert data packet operation in the storagequeue with a revised insert data packet operation if an update datapacket operation is received by the wireless transport module, if theacknowledgement of the data packet has not yet been received from thedestination device, and if the insert data packet operation is not atthe top of the storage queue.
 20. The device of claim 19, wherein therevised insert data packet operation comprises an updated version of thedata packet.
 21. The device of claim 20, wherein the device is furtherconfigured to write the updated version of the data packet to thestorage device if the acknowledgement of the data packet has not yetbeen received from the destination device and if the revised insert datapacket operation is at the top of the storage queue.
 22. The device ofclaim 21, wherein the device is further configured to place a deletedata packet operation in the storage queue to effect removal of theupdated version of the data packet from the storage device if theacknowledgement of the data packet is received from the destinationdevice after the updated version of the data packet is written to thestorage device.
 23. The device of claim 21, wherein the device isfurther configured to place a second update data packet operation in thestorage queue if the second update data packet operation is received bythe wireless transport module and if the acknowledgement of the datapacket has not yet been received from the destination device.
 24. Thedevice of claim 23, wherein the device is further configured to replacethe second update data packet operation with a delete data packetoperation in the storage queue to effect removal of the updated versionof the data packet from the storage device if the acknowledgement of thedata packet is received from the destination device after the secondupdate data packet operation is placed in the storage queue.
 25. Thedevice of claim 20, wherein the device is further configured to removethe revised insert data packet operation from the storage queue if anacknowledgement of the data packet is received from the destinationdevice and if the updated version of the data packet has not beenwritten to the storage device.